Data structures for digests matching in a data deduplication system

ABSTRACT

Data matches are calculated in a data deduplication system by matching input and repository digests using a digest based data matching process where the reference digests corresponding to a repository interval of data identified as similar to an input interval of data are loaded into two data structures. The dual data structures include a sequential buffer containing a plurality of digest entries in a sequence corresponding to a placement order of calculated values of the reference digests, the placement order of the calculated values of the reference digests correlative to an order in which input digest values were calculated such that the plurality of digests are stored in a linear form independent of a deduplicated form by which data the plurality of digests describe is stored.

CROSS REFERENCE TO RELATED APPLICATIONS

The present Application is a Continuation of U.S. patent applicationSer. No. 13/941,886, filed on Jul. 15, 2013, which is cross-related tothe following seventeen Applications each listed as: U.S. applicationSer. No. 13/941,703, U.S. Application No. 13/941,873, U.S. applicationSer. No. 13/941,694, U.S. application Ser. No. 13/941,896, U.S.application Ser. No. 13/941,951, U.S. application Ser. No. 13/941,711,U.S. application Ser. No. 13/941,958, U.S. application Ser. No.13/941,714, U.S. application Ser. No. 13/941,742, U.S. application Ser.No. 13/941,769, U.S. application Ser. No. 13/941,782, U.S. applicationSer. No. 13/941,982, U.S. application Ser. No. 13/941,800, U.S.application Ser. No. 13/941,999, U.S. application Ser. No. 13/942,009,U.S. application Ser. No. 13/942,027, and U.S. application Ser. No.13/942,048, all of which are filed on the same day as the presentinvention and the entire contents of which are incorporated herein byreference and are relied upon for claiming the benefit of priority.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates in general to computers, and moreparticularly to data structures for digests matching in a datadeduplication system in a computing environment.

Description of the Related Art

In today's society, computer systems are commonplace. Computer systemsmay be found in the workplace, at home, or at school. Computer systemsmay include data storage systems, or disk storage systems, to processand store data. Large amounts of data have to be processed daily and thecurrent trend suggests that these amounts will continue beingever-increasing in the foreseeable future. An efficient way to alleviatethe problem is by using deduplication. The idea underlying adeduplication system is to exploit the fact that large parts of theavailable data are copied again and again, by locating repeated data andstoring only its first occurrence. Subsequent copies are replaced withpointers to the stored occurrence, which significantly reduces thestorage requirements if the data is indeed repetitive.

SUMMARY OF THE DESCRIBED EMBODIMENTS

In one embodiment, a method is provided for storing reference digests indual data structures for digests matching in a data deduplication systemusing a processor device in a computing environment. In one embodiment,by way of example only, data matches are calculated in a datadeduplication system by matching input and repository digests using adigest based data matching process where the reference digestscorresponding to a repository interval of data identified as similar toan input interval of data are loaded into two data structures. The dualdata structures include a sequential buffer containing a plurality ofdigest entries in a sequence corresponding to a placement order ofcalculated values of the reference digests, the placement order of thecalculated values of the reference digests correlative to an order inwhich input digest values were calculated such that the plurality ofdigests are stored in a linear form independent of a deduplicated formby which data the plurality of digests describe is stored.

In addition to the foregoing exemplary method embodiment, otherexemplary system and computer product embodiments are provided andsupply related advantages. The foregoing summary has been provided tointroduce a selection of concepts in a simplified form that are furtherdescribed below in the Detailed Description. This Summary is notintended to identify key features or essential features of the claimedsubject matter, nor is it intended to be used as an aid in determiningthe scope of the claimed subject matter. The claimed subject matter isnot limited to implementations that solve any or all disadvantages notedin the background.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the invention will be readilyunderstood, a more particular description of the invention brieflydescribed above will be rendered by reference to specific embodimentsthat are illustrated in the appended drawings. Understanding that thesedrawings depict embodiments of the invention and are not therefore to beconsidered to be limiting of its scope, the invention will be describedand explained with additional specificity and detail through the use ofthe accompanying drawings, in which:

FIG. 1 is a block diagram illustrating a computing system environmenthaving an example storage device in which aspects of the presentinvention may be realized;

FIG. 2 is a block diagram illustrating a hardware structure of datastorage system in a computer system in which aspects of the presentinvention may be realized;

FIG. 3 is a flowchart illustrating an exemplary method for digestretrieval based on similarity search in deduplication processing in adata deduplication system in which aspects of the present invention maybe realized;

FIG. 4 is a flowchart illustrating an exemplary alternative method fordigest retrieval based on similarity search in deduplication processingin a data deduplication system in which aspects of the present inventionmay be realized;

FIG. 5 is a flowchart illustrating an exemplary method for efficientcalculation of both similarity search values and boundaries of digestblocks using a single linear calculation of rolling hash values in adata deduplication system in which aspects of the present invention maybe realized;

FIG. 6 is a block diagram illustrating data structures which aspects ofthe present invention may be realized;

FIG. 7 is a flowchart illustrating an exemplary method for digest baseddata matching in similarity based deduplication in which aspects of thepresent invention may be realized.

DETAILED DESCRIPTION OF THE DRAWINGS

Data deduplication is a highly important and vibrant field in computingstorage systems. Data deduplication refers to the reduction and/orelimination of redundant data. In data deduplication, a data object,which may be a file, a data stream, or some other form of data, isbroken down into one or more parts called chunks or blocks. In a datadeduplication process, duplicate copies of data are reduced oreliminated, leaving a minimal amount of redundant copies, or a singlecopy of the data, respectively. The goal of a data deduplication systemis to store a single copy of duplicated data, and the challenges inachieving this goal are efficiently finding the duplicate data patternsin a typically large repository, and storing the data patterns in astorage efficient deduplicated form. A significant challenge indeduplication storage systems is scaling to support very largerepositories of data. Such large repositories can reach sizes ofPetabytes (1 Petabyte=2⁵⁰ bytes) or more. Deduplication storage systemssupporting such repository sizes, must provide efficient processing forfinding duplicate data patterns within the repositories, whereefficiency is measured in resource consumption for achievingdeduplication (resources may be CPU cycles, RAM storage, persistentstorage, networking, etc.). In one embodiment, a deduplication storagesystem may be based on maintaining a search optimized index of valuesknown as fingerprints or digests, where a (small) fingerprint representsa (larger) block of data in the repository. The fingerprint values maybe cryptographic hash values calculated based on the blocks' data. Inone embodiment, secure hash algorithm (SHA), e.g. SHA-1 or SHA-256,which are a family of cryptographic hash functions, may be used.Identifying fingerprint matches, using index lookup, enables to storereferences to data that already exists in a repository. In oneembodiment, content defined chunking may be used in for determiningsegment boundaries where the boundaries are based on the data itself.

To provide reasonable deduplication in this approach, the mean size ofthe data blocks based on which fingerprints are generated must belimited to smaller sizes and may not be too large. The reason being thata change of a bit within a data block will probabilistically change thedata block's corresponding fingerprint, and thus having large datablocks makes the scheme more sensitive to updates in the data ascompared to having small blocks. A typical data block size may rangefrom 4KB to 64KB, depending on the type of application and workload.Thus, by way of example only, small data blocks may range in sizes of upto 64KB, and large data blocks are those data blocks having a sizelarger than 64KB.

To support very large repositories scaling to Petabytes (e.g.,repositories scaling to at least one Petabyte), the number offingerprints to store coupled with the size of a fingerprint (rangingbetween 16 bytes and 64 bytes), becomes prohibitive. For example, for 1Petabyte of deduplicated data, with a 4KB mean data block size, and 32bytes fingerprint size (e.g. of SHA-256), the storage required to storethe fingerprints is 8 Terabytes. Maintaining a search optimized datastructure for such volumes of fingerprints is difficult, and requiresoptimization techniques. However existing optimization techniques do notscale to these sizes while maintaining performance. For this reason, toprovide reasonable performance, the supported repositories have to berelatively small (on the order of tens of TB). Even for such smallersizes, considerable challenges and run-time costs arise due to the largescale of the fingerprint indexes, that create a bottle-neck (e.g., achunk look disk bottleneck) in deduplication processing. A solid-statedisk (SSD) to cache parts of the index in low persistent memory may beused but such is limited by the size and cost of the SSD.

To solve this problem, in one embodiment, a deduplication system may bebased on a two-step approach for searching data patterns duringdeduplication. In the first step, a large chunk of incoming data (e.g. afew megabytes) is searched in the repository for similar (rather thanidentical) data chunks of existing data, and the incoming data chunk ispartitioned accordingly into intervals and paired with corresponding(similar) repository intervals. In the second step, a byte-wise matchingalgorithm is applied on pairs of similar intervals, to identifyidentical sub-intervals, which are already stored in a repository ofdata. The matching algorithm of the second step relies on reading allthe relevant similar data in the repository in order to compare itbyte-wise to the input data.

Yet, a problem stemming from a byte-wise comparison of data underlyingthe matching algorithm of the second step, is that data of roughly thesame size and rate as the incoming data should be read from therepository, for comparison purposes. For example, a system processing 1GB of incoming data per second, should read about 1 GB of data persecond from the repository for byte-wise comparison. This requiressubstantially high capacities of I/O per second of the storage devicesstoring the repository data, which in turn increases their cost.

Additional trends in information technology coinciding with the aboveproblem are the following: (1) Improvements in the computing ability byincreasing CPU speeds and the number of CPU cores. (2) Increase in diskdensity, while disk throughput remains relatively constant or improvingonly modestly. This means that there are fewer spindles relative to thedata capacity, thus practically reducing the overall throughput. Due tothe problem specified above, there is a need to design an alternativesolution, to be integrated in a two step deduplication system embodimentspecified above, that does not require reading from the repository inhigh rates/volumes.

Therefore, in one embodiment, by way of example only, additionalembodiments address these problems, as well as shifts resourceconsumption from disks to the CPUs, to benefit from the above trends.The embodiments described herein are integrated within the two-step andscalable deduplication embodiments embodiment described above, and usesa similarity search to focus lookup of digests during deduplication. Inone embodiment, a global similarity search is used as a basis forfocusing the similarity search for digests of repository data that ismost likely to match input data.

The embodiments described herein significantly reduce the capacity ofI/O per second required of underlying disks, benefit from the increasesin computing ability and in disk density, and considerably reduce thecosts of processing, as well as maintenance costs and environmentaloverhead (e.g. power consumption).

In one embodiment, input data is segmented into small segments (e.g.4KB) and a digest (a cryptographic hash value, e.g. SHA1) is calculatedfor each such segment. First, a similarity search algorithm, asdescribed above, is applied on an input chunk of data (e.g. 16MB), andthe positions of the most similar reference data in the repository arelocated and found. These positions are then used to lookup the digestsof the similar reference data. The digests of all the data contained inthe repository are stored and retrieved in a form that corresponds totheir occurrence in the data. Given a position of a section of datacontained in the repository, the digests associated with the section ofdata are efficiently located in the repository and retrieved. Next,these reference digests are loaded into memory, and instead of comparingdata to find matches, the input digests and the loaded reference digestsare matched.

The described embodiments provide a new fundamental approach forarchitecting a data deduplication system, which integrates a scalabletwo step approach of similarity search followed by a search of identicalmatching segments, with an efficient and cost effectivedigest/fingerprint based matching algorithm (instead of byte-wise datacomparison). The digest/fingerprint based matching algorithm enables toread only a small fraction (1%) of the volume of data required bybyte-wise data comparison. The present invention proposed herein, adeduplication system can provide high scalability to very large datarepositories, in addition to high efficiency and performance, andreduced costs of processing and hardware.

In one embodiment, by way of example only, the term “similar data” maybe referred to as: for any given input data, data which is similar tothe input data is defined as data which is mostly the same (i.e. notentirely but at least 50% similar) as the input data. From looking atthe data in a binary view (perspective), this means that similar data isdata where most (i.e. not entirely but at least 50% similar) of thebytes are the same as the input data.

In one embodiment, by way of example only, the term “similar search” maybe referred to as the process of searching for data which is similar toinput data in a repository of data. In one embodiment, this process maybe performed using a search structure of similarity elements, which ismaintained and searched within.

In one embodiment, by way of example only, the term “similarityelements” may be calculated based on the data and facilitate a globalsearch for data which is similar to input data in a repository of data.In general, one or more similarity elements are calculated, andrepresent, a large (e.g. at least 16 MB) chunk of data.

Thus, the various embodiments described herein provide various solutionsfor digest retrieval based on a similarity search in deduplicationprocessing in a data deduplication system using a processor device in acomputing environment. In one embodiment, by way of example only, inputdata is partitioned into fixed sized data chunks. Similarity elements,digest block boundaries and digest values are calculated for each of thefixed sized data chunks. Matching similarity elements are searched forin a search structure (i.e. index) containing the similarity elementsfor each of the fixed sized data chunks in a repository of data.Positions of similar data are located in a repository. The positions ofthe similar data are used to locate and load into the memory storeddigest values and corresponding stored digest block boundaries of thesimilar data in the repository. It should be noted that in oneembodiment the positions may be either physical or logical (i.e.virtual). The positions are of data inside a repository of data. Theimportant property of a ‘position’ is that given a position (physical orlogical) in the repository's data, the data in that position can beefficiently located and accessed. The digest values and thecorresponding digest block boundaries are matched with the stored digestvalues and the corresponding stored digest block boundaries to find datamatches.

Thus, the various embodiments described herein provide various solutionsfor digest retrieval based on a similarity search in deduplicationprocessing in a data deduplication system using a processor device in acomputing environment. In one embodiment, by way of example only, inputdata is partitioned into fixed sized data chunks. Similarity elements,digest block boundaries and digest values are calculated for each of thefixed sized data chunks. Matching similarity elements are searched forin a search structure (i.e. index) containing the similarity elementsfor each of the fixed sized data chunks in a repository of data.Positions of similar data are located in a repository. The positions ofthe similar data are used to locate and load into the memory storeddigest values and corresponding stored digest block boundaries of thesimilar data in the repository. The digest values and the correspondingdigest block boundaries are matched with the stored digest values andthe corresponding stored digest block boundaries to find data matches

In one embodiment, the present invention provides a solution forutilizing a similarity search to load into memory the relevant digestsfrom the repository, for efficient deduplication processing. In a datadeduplication system, deduplication is performed by partitioning thedata into large fixed sized chunks, and for each chunk calculating (2things—similarity elements and digest blocks/digest values) hash values(digest block/digest value) for similarity search and digest values. Thedata deduplication system searches for matching similarity values of thechunks in a search structure of similarity values, and finds thepositions of similar data in the repository. The data deduplicationsystem uses these positions of similar data to locate and load intomemory stored digests of the similar repository data, and matching inputand repository digest values to find data matches.

In one embodiment, the present invention provides for efficientcalculation of both similarity search values and segmentation (i.e.boundaries) of digest blocks using a single linear calculation ofrolling hash values. In a data deduplication system, the input data ispartitioned into chunks, and for each chunk a set of rolling hash valuesis calculated. A single linear scan of the rolling hash values producesboth similarity search values and boundaries of the digest blocks of thechunk. Each rolling hash value corresponds to a consecutive window ofbytes in byte offsets. The similarity search values are used to searchfor similar data in the repository. The digest blocks segmentation isused to calculate digest block boundaries and corresponding digestvalues of the chunk, for digests matching. Each rolling hash valuecontributes to the calculation of the similarity values and to thecalculation of the digest blocks segmentations. Each rolling hash valuemay be discarded after contributing to the calculations. The describedembodiment provides significant processing efficiency and reduction ofCPU consumption, as well as considerable performance improvement.

Thus, as described above, the deduplication approach of the presentinvention uses a two-step process for searching data patterns duringdeduplication. In the first step, a large chunk of incoming data (e.g.16 megabytes “MB”) is searched in the repository for similar (ratherthan identical) chunks of existing data, and the incoming chunk ispartitioned accordingly into intervals, and paired with corresponding(similar) repository intervals. The similarity search structure (or“index”) used in the first step is compact and simple to maintain andsearch within, because the elements used for a similarity search arevery compact relative to the data they represent (e.g. 16 bytesrepresenting 4 megabytes). Further included in the first step, inaddition to a calculation of similarity elements, is a calculation ofdigest segments and respective digest values for the input chunk ofdata. All these calculations are based on a single calculation ofrolling hash values. In the second step, reference digests of thesimilar repository intervals are retrieved, and then the input digestsare matched with the reference digests, to identify data matches.

In one embodiment, in the similarity based deduplication approach asdescribed herein, a stream of input data is partitioned into chunks(e.g. at least 16 MB), and each chunk is processed in two main steps. Inthe first step a similarity search process is applied, and positions ofthe most similar reference data in the repository are found. Within thisstep both similarity search elements and digest segments boundaries arecalculated for the input chunk, based on a single linear calculation ofrolling hash values. Digest values are calculated for the input chunkbased on the produced segmentation, and stored in memory in the sequenceof their occurrence in the input data. The positions of similar data arethen used to lookup the digests of the similar reference data and loadthese digests into memory, also in a sequential form. Then, the inputdigests are matched with the reference digests to form data matches.

When deduplication of an input chunk of data is complete, the inputchunk of data's associated digests are stored in the repository, toserve as reference digests for subsequent input data. The digests arestored in a linear form, which is independent of the deduplicated formby which the data these digests describe is stored, and in the sequenceof their occurrence in the data. This method of storage enablesefficient retrieval of sections of digests, independent of fragmentationcharacterizing deduplicated storage forms, and thus low on IO andcomputational resource consumption.

In addition, to solve the bottleneck problem as described above, in oneembodiment, a deduplication system, as described herein, may use the twostep approach for searching data patterns during deduplication. In thefirst step, a large chunk of incoming data (e.g. a few megabytes) issearched in the repository for similar (rather than identical) datachunks of existing data, and the incoming data chunk is partitionedaccordingly into intervals and paired with corresponding (similar)repository intervals. In the second step, a byte-wise matching algorithmis applied on pairs of similar intervals, to identify identicalsub-intervals, which are already stored in a repository of data. Thesimilarity index used in this step is very compact and simple tomaintain and search within, since the elements used for similaritysearch are very compact relative to the data they represent (e.g. 16bytes representing 4 megabytes). Further included in the first step is acalculation of similarity characteristics as well as digest segments andrespective digest values, of the input chunk of data. These calculationsare based on a single calculation of rolling hash values. The matchingalgorithm of the second step relies on reading all the relevant similardata in the repository in order to compare it byte-wise to the inputdata. In the second step, reference digests of the similar repositoryintervals are retrieved, and then the input digests are matched with thereference digests, to identify data matches. This approach works verywell on data sets where the generations of data have a low to moderatechange rate (roughly up to 30% change rate) relative to previousgenerations. Such change rates are very typical for the most common usecases, and are specifically typical for data backup environments.

However, in the second step the existing matching algorithm searches foreach individual input digest in the reference digests, which is acomputationally intensive process. Another implication of the individualsearch is that relatively small data matches are produced, even in caseswhere such data matches are subsets of larger matches, which isinefficient in terms of storage considerations.

Due to the problem specified above, there is a need to design a digestsmatching algorithm that will reduce the number of digest searchoperations and will produce the largest possible data matches. Thisalgorithm should also benefit from the fact that in the presentinvention digests are retrieved from the repository in a form thatcorresponds to their order of occurrence in the repository data.

In one embodiment, by way of example only, the present inventionprovides a digests matching algorithm that solves this problem, as wellas benefits from the form in which digests are retrieved. The presentinvention provides considerable additional efficiency, both incomputational and storage efficiency perspectives, that further enhancesthe performance and scalability of our similarity based deduplicationapproach.

In one embodiment, by way of example only, in the first step, asdescribed herein, a similarity search process is applied on an inputchunk of data (e.g. 16MB), and the positions of the most similarreference data in the repository are found. Within this step bothsimilarity search elements and digest segments boundaries are calculatedfor the input chunk, based on a single linear calculation of rollinghash values. Digest values are calculated for the input chunk based onthe produced segmentation, and stored in a memory buffer in the sequenceof their occurrence in the input data. The positions of similar data arethen used to lookup the digests of the similar reference data. In oneembodiment, the digests of the data contained in the repository arestored and retrieved in a form that corresponds to their occurrence inthe data. Given a position and size of a section of data contained inthe repository, its associated digests are efficiently located in therepository and retrieved. After the reference digests of the similarrepository data are retrieved (and as the input digests are alreadycalculated and available), the present invention, as described below, isinitiated.

In one embodiment, the present invention loads the reference digestsinto two structures in memory: a buffer containing the digestssequentially in the order of their occurrence in the data, and a searchstructure, e.g. a hash table. Each digest value of the input chunk issearched in the search structure, and each candidate in the searchstructure, pointing into the buffer, is verified using the referencedigest value and corresponding segment size. A match is declared only ifboth these values match. Each of the matches found is then extendedforward and backward using the buffer of reference digests, until thematched sequence of digests cannot be further extended. The largestmatched sequence is selected, and a data match, between the input andrepository data, corresponding to the data covered by the matcheddigests sequence, is generated. If no match is found for the inputdigest, then the input data covered by that digest is determined to benot found in the repository, and a data mismatch is declared for thatinput data segment. The algorithm of the present invention thencontinues to process the next input digest, immediately following thecurrently matched sequence of input digests, or immediately followingthe currently mismatched input digest.

In one embodiment, for the dual data structures employed by thealgorithm to store the reference digests—a sequential buffer (forextension of matches) and a search structure e.g. hash table (forefficient search of reference digests matching a given version digest),in a data deduplication system, matches of input and repository data arecalculated by a digest based matching algorithm where the digestscorresponding to a repository interval of data, identified as similar toa given input interval, are loaded into two memory structures: asequential buffer containing a plurality of digests in the sequence oftheir occurrence in the data, and a search structure. An interval ofdata is specified by a starting position and size. A digest entryincludes its value, and its segment's position and size in the data. Inone embodiment, the search data structure may be a hash table. In oneembodiment, storing repository digests in a sequential buffer may beused for extension of single matching digests into additional adjacentdigests, and storing repository digests in a search structure may beused for efficient search of repository digests matching a given inputdigest.

In one embodiment, for utilization of the two data structures used bythe algorithm, for finding matching digests and for extending matcheswith adjacent matching digests, in a data deduplication system, matchesof input and repository data are calculated by a digest based matchingalgorithm where a repository digests corresponding to a repositoryinterval of data, identified as similar to a given interval of inputdata, are loaded into a sequential representation and into a searchstructure, and for each digest match found in the search structure thematch is extended using a sequential representation of the repositorydigests. An interval of data is specified by a starting position andsize. A digest entry includes its value, and its segment's position andsize in the data. In one embodiment, a search data structure may be ahash table. A sequential representation of repository digests may be asequential buffer containing a plurality of repository digests,appearing in the sequence of their occurrence in the data. In oneembodiment, input digests are searched in a search structure. Anextension of a digest match is done by matching digests adjacent to aninitial match in forward and backward directions, until a matchedsequence of digests cannot be further extended. A largest matchedsequence of matched sequences, is selected.

In one embodiment, for optimization where the hash table entries containonly a compact index (e.g. of 2 bytes) that points into a sequentialbuffer (instead of containing the complete digest information), theoptimization makes the hash table very compact, and saves a considerableamount of memory. In one embodiment, in a data deduplication system,digests corresponding to an interval of repository data are loaded intotwo memory structures, a sequential representation and a searchstructure, and the entries of the search structure contain a compactindex pointing into the sequential representation of digests. Aninterval of data is specified by a starting position and size. A digestentry in the sequential representation includes the digest value, andits segment's position and size in the data. In one embodiment, a searchdata structure may be a hash table. A sequential representation ofrepository digests may be a sequential buffer containing a plurality ofrepository digests, appearing in the sequence of their occurrence in thedata.

In one embodiment, for optimization where information produced by apreliminary step of similarity search, consisting of already verifiedmatching positions in the input and the repository intervals is usedwithin a first step of extending matching digest sequences anchored atthe aforementioned verified matching positions, before proceeding to asecond step of finding further matches considering only the remainingunmatched input digests, in a data deduplication system, matches ofinput and repository data are calculated by a digest based matchingalgorithm, where in a first step digest matches, anchored at alreadyverified matching positions in the input and repository data, areextended to create data matches, and in a second step the remainingunmatched input digests are matched. An interval of data is specified bya starting position and a size. The already verified matching positionsmay be produced by a prior step of similarity search. The first stepincludes comparing the digests at the anchor positions, and if theirvalues and segment sizes match, then an extension of the match isapplied forward and backward onto adjacent digests. A sequence ofmatching digests is extended onto adjacent digests until the sequencecannot be further extended. The second step includes searching for theinput digests, which were not matched in the first step, in a hashtable. A matching sequence of digests is recorded as a match of theinput and repository intervals of data covered by the sequence ofdigests.

In one embodiment, the present invention stores reference digests indual data structures in a digest based data matching process in a datadeduplication system using a processor device in a computingenvironment. In one embodiment, by way of example only, a repositorydata interval is determined as similar to an input data interval. Thereference digests corresponding to the repository data interval areloaded into dual data structures. The dual data structures include asequential buffer containing multiple digest entries in a sequence ofoccurrence in data, and a search structure for searching of thereference digests matching an input digest.

In one embodiment, by way of example only, the present inventioncalculates data matches between input data and repository data in a datadeduplication system using a processor device. A repository datainterval is determined as similar to an input data interval. Repositorydigests corresponding to the similar repository data interval are loadedinto a sequential representation and into a search structure. Matches ofinput digests and repository digests are found using the searchstructure. Each one of the found matches of the input digests and therepository digests are extended using the sequential representation.Data matches are found between the input data and the repository datausing the extended matches of digests.

In one embodiment, by way of example only, the present inventionoptimizes a calculation of data matches between input data andrepository data in a digest based data matching process in a datadeduplication system using a processor device in a computingenvironment. A repository data interval is determined as similar to aninput data interval. Repository digests corresponding to the similarrepository data interval are loaded into a sequential representation andinto a search structure. Digest matches are identified between inputdigests and the repository digests where the digest matches are locatedat anchored positions in input data and in repository data, and thesedigest matches are extended. The digest matches are calculated betweenremaining unmatched input digests and the plurality of repositorydigests. The data matches are determined between the input data and therepository data using the calculated matches of digests.

In one embodiment, by way of example only, the present inventionoptimizes a hash table structure for digest matching in a datadeduplication system using a processor device in a computingenvironment. A repository data interval is determined as similar to aninput data interval. Repository digests corresponding to the similarrepository data interval are loaded into a sequential representation andinto a search structure.

Turning now to FIG. 1, exemplary architecture 10 of a computing systemenvironment is depicted. The computer system 10 includes centralprocessing unit (CPU) 12, which is connected to communication port 18and memory device 16. The communication port 18 is in communication witha communication network 20. The communication network 20 and storagenetwork may be configured to be in communication with server (hosts) 24and storage systems, which may include storage devices 14. The storagesystems may include hard disk drive (HDD) devices, solid-state devices(SSD) etc., which may be configured in a redundant array of independentdisks (RAID). The operations as described below may be executed onstorage device(s) 14, located in system 10 or elsewhere and may havemultiple memory devices 16 working independently and/or in conjunctionwith other CPU devices 12. Memory device 16 may include such memory aselectrically erasable programmable read only memory (EEPROM) or a hostof related devices. Memory device 16 and storage devices 14 areconnected to CPU 12 via a signal-bearing medium. In addition, CPU 12 isconnected through communication port 18 to a communication network 20,having an attached plurality of additional computer host systems 24. Inaddition, memory device 16 and the CPU 12 may be embedded and includedin each component of the computing system 10. Each storage system mayalso include separate and/or distinct memory devices 16 and CPU 12 thatwork in conjunction or as a separate memory device 16 and/or CPU 12.

FIG. 2 is an exemplary block diagram 200 showing a hardware structure ofa data storage system in a computer system according to the presentinvention. Host computers 210, 220, 225, are shown, each acting as acentral processing unit for performing data processing as part of a datastorage system 200. The cluster hosts/nodes (physical or virtualdevices), 210, 220, and 225 may be one or more new physical devices orlogical devices to accomplish the purposes of the present invention inthe data storage system 200. In one embodiment, by way of example only,a data storage system 200 may be implemented as IBM® ProtecTIER®deduplication system TS7650G™. A Network connection 260 may be a fibrechannel fabric, a fibre channel point to point link, a fibre channelover ethernet fabric or point to point link, a FICON or ESCON I/Ointerface, any other I/O interface type, a wireless network, a wirednetwork, a LAN, a WAN, heterogeneous, homogeneous, public (i.e. theInternet), private, or any combination thereof. The hosts, 210, 220, and225 may be local or distributed among one or more locations and may beequipped with any type of fabric (or fabric channel) (not shown in FIG.2) or network adapter 260 to the storage controller 240, such as Fibrechannel, FICON, ESCON, Ethernet, fiber optic, wireless, or coaxialadapters. Each of the hosts, 210, 220, and 225 may also be incommunication and association with the storage controller 240. Datastorage system 200 is accordingly equipped with a suitable fabric (notshown in FIG. 2) or network adaptor 260 to communicate. Data storagesystem 200 is depicted in FIG. 2 comprising storage controllers 240 andcluster hosts 210, 220, and 225. The cluster hosts 210, 220, and 225 mayinclude cluster nodes.

To facilitate a clearer understanding of the methods described herein,storage controller 240 is shown in FIG. 2 as a single processing unit,including a microprocessor 242, system memory 243 and nonvolatilestorage (“NVS”) 216. It is noted that in some embodiments, storagecontroller 240 is comprised of multiple processing units, each withtheir own processor complex and system memory, and interconnected by adedicated network within data storage system 200. Storage 230 (labeledas 230 a, 230 b, and 230 n in FIG. 3) may be comprised of one or morestorage devices, such as storage arrays, which are connected to storagecontroller 240 (by a storage network) with one or more cluster hosts210, 220, and 225 connected to each storage controller 240.

In some embodiments, the devices included in storage 230 may beconnected in a loop architecture. Storage controller 240 manages storage230 and facilitates the processing of write and read requests intendedfor storage 230. The system memory 243 of storage controller 240 storesprogram instructions and data, which the processor 242 may access forexecuting functions and method steps of the present invention forexecuting and managing storage 230 as described herein. In oneembodiment, system memory 243 includes, is in association with, or is incommunication with the operation software 250 for performing methods andoperations described herein. As shown in FIG. 2, system memory 243 mayalso include or be in communication with a cache 245 for storage 230,also referred to herein as a “cache memory”, for buffering “write data”and “read data”, which respectively refer to write/read requests andtheir associated data. In one embodiment, cache 245 is allocated in adevice external to system memory 243, yet remains accessible bymicroprocessor 242 and may serve to provide additional security againstdata loss, in addition to carrying out the operations as described inherein.

In some embodiments, cache 245 is implemented with a volatile memory andnon-volatile memory and coupled to microprocessor 242 via a local bus(not shown in FIG. 2) for enhanced performance of data storage system200. The NVS 216 included in data storage controller is accessible bymicroprocessor 242 and serves to provide additional support foroperations and execution of the present invention as described in otherfigures. The NVS 216, may also referred to as a “persistent” cache, or“cache memory” and is implemented with nonvolatile memory that may ormay not utilize external power to retain data stored therein. The NVSmay be stored in and with the cache 245 for any purposes suited toaccomplish the objectives of the present invention. In some embodiments,a backup power source (not shown in FIG. 2), such as a battery, suppliesNVS 216 with sufficient power to retain the data stored therein in caseof power loss to data storage system 200. In certain embodiments, thecapacity of NVS 216 is less than or equal to the total capacity of cache245.

Storage 230 may be physically comprised of one or more storage devices,such as storage arrays. A storage array is a logical grouping ofindividual storage devices, such as a hard disk. In certain embodiments,storage 230 is comprised of a JBOD (Just a Bunch of Disks) array or aRAID (Redundant Array of Independent Disks) array. A collection ofphysical storage arrays may be further combined to form a rank, whichdissociates the physical storage from the logical configuration. Thestorage space in a rank may be allocated into logical volumes, whichdefine the storage location specified in a write/read request.

In one embodiment, by way of example only, the storage system as shownin FIG. 2 may include a logical volume, or simply “volume,” may havedifferent kinds of allocations. Storage 230 a, 230 b and 230 n are shownas ranks in data storage system 200, and are referred to herein as rank230 a, 230 b and 230 n. Ranks may be local to data storage system 200,or may be located at a physically remote location. In other words, alocal storage controller may connect with a remote storage controllerand manage storage at the remote location. Rank 230 a is shownconfigured with two entire volumes, 234 and 236, as well as one partialvolume 232 a. Rank 230 b is shown with another partial volume 232 b.Thus volume 232 is allocated across ranks 230 a and 230 b. Rank 230 n isshown as being fully allocated to volume 238—that is, rank 230 n refersto the entire physical storage for volume 238. From the above examples,it will be appreciated that a rank may be configured to include one ormore partial and/or entire volumes. Volumes and ranks may further bedivided into so-called “tracks,” which represent a fixed block ofstorage. A track is therefore associated with a given volume and may begiven a given rank.

The storage controller 240 may include a data duplication module 255, asimilarity index module 257 (e.g., a similarity search structure), and asimilarity search module 259. The data duplication module 255, thesimilarity index module 257, and the similarity search module 259 maywork in conjunction with each and every component of the storagecontroller 240, the hosts 210, 220, 225, and storage devices 230. Thedata duplication module 255, the similarity index module 257, and thesimilarity search module 259 may be structurally one complete module ormay be associated and/or included with other individual modules. Thedata duplication module 255, the similarity index module 257, and thesimilarity search module 259 may also be located in the cache 245 orother components.

The storage controller 240 includes a control switch 241 for controllingthe fiber channel protocol to the host computers 210, 220, 225, amicroprocessor 242 for controlling all the storage controller 240, anonvolatile control memory 243 for storing a microprogram (operationsoftware) 250 for controlling the operation of storage controller 240,data for control, cache 245 for temporarily storing (buffering) data,and buffers 244 for assisting the cache 245 to read and write data, acontrol switch 241 for controlling a protocol to control data transferto or from the storage devices 230, the data duplication module 255, thesimilarity index module 257, and the similarity search module 259, inwhich information may be set. Multiple buffers 244 may be implementedwith the present invention to assist with the operations as describedherein. In one embodiment, the cluster hosts/nodes, 210, 220, 225 andthe storage controller 240 are connected through a network adaptor (thiscould be a fibre channel) 260 as an interface i.e., via at least oneswitch called “fabric.”

In one embodiment, the host computers or one or more physical or virtualdevices, 210, 220, 225 and the storage controller 240 are connectedthrough a network (this could be a fibre channel) 260 as an interfacei.e., via at least one switch called “fabric.” In one embodiment, theoperation of the system shown in FIG. 2 will be described. Themicroprocessor 242 may control the memory 243 to store commandinformation from the host device (physical or virtual) 210 andinformation for identifying the host device (physical or virtual) 210.The control switch 241, the buffers 244, the cache 245, the operatingsoftware 250, the microprocessor 242, memory 243, NVS 216, dataduplication module 255, the similarity index module 257, and thesimilarity search module 259 are in communication with each other andmay be separate or one individual component(s). Also, several, if notall of the components, such as the operation software 250 may beincluded with the memory 243. Each of the components within the devicesshown may be linked together and may be in communication with each otherfor purposes suited to the present invention. As mentioned above, thedata duplication module 255, the similarity index module 257, and thesimilarity search module 259 may also be located in the cache 245 orother components. As such, the data duplication module 255, thesimilarity index module 257, and the similarity search module 259 may beused as needed, based upon the storage architecture and users'preferences.

As mentioned above, in one embodiment, the input data is partitionedinto large fixed size chunks (e.g. 16 MB), and a similarity searchprocedure is applied for each input chunk. A similarity search procedurecalculates compact similarity elements, which may also be referred to asdistinguishing characteristics (DCs), based on the input chunk of data,and searches for matching similarity elements stored in a compact searchstructure (i.e. index) in the repository. The size of the similarityelements stored per each chunk of data is typically 32 bytes (where thechunk size is a few megabytes), thus making the search structure storingthe similarity elements very compact and simple to maintain and searchwithin.

The similarity elements are calculated by calculating rolling hashvalues on the chunk's data, namely producing a rolling hash value foreach consecutive window of bytes in a byte offset, and then selectingspecific hash values and associated positions (not necessarily the exactpositions of these hash values) to be the similarity elements of thechunk.

One important aspect and novelty provided by the present invention isthat a single linear calculation of rolling hash values, which is acomputationally expensive operation, serves as basis for calculatingboth the similarity elements of a chunk (for a similarity search) andthe segmentation of the chunk's data into digest blocks (for findingexact matches). Each rolling hash value is added to the calculation ofthe similarity elements as well as to the calculation of the digestblocks segmentation. After being added to the two calculations, arolling hash value can be discarded, as the need to store the rollinghash values is minimized or eliminated. This algorithmic elementprovides significant efficiency and reduction of CPU consumption, aswell as considerable performance improvement.

In one embodiment, the similarity search procedure of the presentinvention produces two types of output. The first type of output is aset of positions of the most similar reference data in the repository.The second type of output is the digests of the input chunk, comprisingof the segmentation to digest blocks and the digest values correspondingto the digest blocks, where the digest values are calculated based onthe data of the digest blocks.

In one embodiment, the digests are stored in the repository in a formthat corresponds to the digests occurrence in the data. Given a positionin the repository and size of a section of data, the location in therepository of the digests corresponding to that interval of data isefficiently determined. The positions produced by the similarity searchprocedure are then used to lookup the stored digests of the similarreference data, and to load these reference digests into memory. Then,rather than comparing data, the input digests and the loaded referencedigests are matched. The matching process is performed by loading thereference digests into a compact search structure of digests in memory,and then for each input digest, querying the search structure of digestsfor existence of that digest value. Search in the search structure ofdigests is performed based on the digest values. If a match is found,then the input data associated with that digest is determined to befound in the repository and the position of the input data in therepository is determined based on the reference digest's position in therepository. In this case, the identity between the input data covered bythe input digest, and the repository data covered by the matchingreference digest, is recorded. If a match is not found then the inputdata associated with that digest is determined to be not found in therepository, and is recorded as new data. In one embodiment, thesimilarity search structure is a global search structure of similarityelements, and a memory search structure of digests' is a local searchstructure of digests in memory. The search in the memory searchstructure of digests is performed by the digest values.

FIG. 3 is a flowchart illustrating an exemplary method 300 for digestretrieval based on similarity search in deduplication processing in adata deduplication system in which aspects of the present invention maybe realized. The method 300 begins (step 302). The method 300 partitionsinput data into data chunks (step 304). The input data may bepartitioned into fixed sized data chunks. The method 300 calculates, foreach of the data chunks, similarity elements, digest block boundaries,and corresponding digest values are calculated (step 306). The method300 searches for matching similarity elements in a search structure(i.e. index) for each of the data chunks (which may be fixed size datachunks) (step 308). The positions of the similar data in a repository(e.g., a repository of data) are located (step 310). The method 300 usesthe positions of the similar data to locate and load into memory storeddigest values and corresponding stored digest block boundaries of thesimilar data in the repository (step 312). The method 300 matches thedigest values and the corresponding digest block boundaries of the inputdata with the stored digest values and the corresponding stored digestblock boundaries to find data matches (step 314). The method 300 ends(step 316).

FIG. 4 is a flowchart illustrating an exemplary alternative method 400for digest retrieval based on similarity search in deduplicationprocessing in a data deduplication system in which aspects of thepresent invention may be realized. The method 400 begins (step 402). Themethod 400 partitions the input data into chunks (e.g., partitions theinput data into large fixed size chunks) (step 404), and for an inputdata chunk calculates rolling hash values, similarity elements, digestblock boundaries, and digest values based on data of the input datachunk (step 406). The method 400 searches for similarity elements of theinput data chunk in a similarity search structure (i.e. index) (step 408and 410). The method 400 determines if there are enough or a sufficientamount of matching similarity elements (step 412). If not enoughmatching similarity elements are found then the method 400 determinesthat no similar data is found in the repository for the input datachunk, and the data of the input chunk is stored in a repository (step414) and then the method 400 ends (step 438). If enough similarityelements are found, then for each similar data interval found in arepository, the method 400 determines the position and size of eachsimilar data interval in the repository (step 416). The method 400locates the digests representing the similar data interval in therepository (step 418). The method 400 loads these digests into a searchdata structure of digests in memory (step 420). The method 400determines if there are any additional similar data intervals (step422). If yes, the method 400 returns to step 416. If no, the method 400considers each digest of the input data chunk (step 424). The method 400determines if the digest value exists in the memory search structure ofdigests (step 426). If yes, the method 400 records the identity betweenthe input data covered by the digest and the repository data having thematching digest value (step 428). If no, the method 400 records that theinput data covered by the digest is not found in the repository (step430). From both steps 428 and 430, the method 400 determines if thereare additional digests of the input data chunk (step 432). If yes, themethod 400 returns to step 424. If no, method 400 removes the similarityelements of the matched data in the repository from the similaritysearch structure (step 434 and step 410). The method 400 adds thesimilarity elements of the input data chunk to the similarity searchstructure (step 436). The method 400 ends (step 438).

FIG. 5 is a flowchart illustrating an exemplary method 500 for efficientcalculation of both similarity search values and boundaries of digestblocks using a single linear calculation of rolling hash values in adata deduplication system in which aspects of the present invention maybe realized. The method 500 begins (step 502). The method 500 partitionsinput data into data chunks (steps 504). The data chunks may be fixedsized data chunks. The method 500 considers each consecutive window ofbytes in a byte offset in the input data (step 506). The method 500determines if there is an additional consecutive window of bytes to beprocessed (step 508). If yes, the method 500 calculates a rolling hashvalue based on the data of the consecutive window of bytes (step 510).The method 500 contributes the rolling hash value to the calculation ofthe similarity values and to the calculation of the digest blockssegmentations (i.e., the digest block boundaries) (step 512). The method500 discards the rolling hash value (step 514), and returns to step 506.If no, the method 500 concludes the calculation of the similarityelements and of the digest blocks segmentation, producing the finalsimilarity elements and digest blocks segmentation of the input data(step 516). The method 500 calculates digest values based on the digestblocks segmentation, wherein each digest block is assigned with acorresponding digest value (step 518). The similarity elements are usedto search for similar data in the repository (step 520). The digestblocks and corresponding digest values are used for matching with digestblocks and corresponding digest values stored in a repository fordetermining data in the repository which is identical to the input data(step 522). The method 500 ends (step 524).

FIG. 6 is a block diagram illustrating a memory structures which aspectsof the present invention may be realized. In one embodiment, asdescribed in FIG. 6, the global cache 600 consists of digest records 606(shown in FIG. 6 as 606A-H) stored in a sequential form in the memory600. The hash table 610 contains entries 612 (shown in FIG. 6 as 612A-G)that point to a list of indexes 608 that point into the digest records606. In the hash table 610 entries 612 are included inside the hashtable 612, where the entry 612 is linked to the entries list 608 of thetable bucket where the digest value is hashed to. Each entry 612consists of two compact indexes 608, one pointing to a digest record606, and the second pointing to a digest entry position inside thedigest record. The hash table 610 enables to efficiently search withinthe memories contents.

FIG. 7 is a flowchart illustrating an exemplary method 700 for digestbased data matching in similarity based deduplication in a datadeduplication system in which aspects of the present invention may berealized. The method 700 begins (step 702). The method 700 includesinputs a pair of similar versions (step 703). Each interval is specifiedby a starting position and size. The method 700 retrieves from therepository the digests corresponding to the reference interval (step704). The method 700 loads the reference digests into memory, and storethem in two forms (see FIG. 6) (step 706). In one embodiment, a buffercontains the digests are stored sequentially in the order of theiroccurrence in the data. Each digest entry includes the digest value, andits segment's position and size in the data. A search structure may be ahash table. The method 700 calculates digests for the version intervaland considers each such digest, and/or alternatively obtains the digestsfrom a previous process, which already calculated these digests (step708). These digests are stored in a memory buffer in the sequence oftheir occurrence in the input data. The method 700 determines if thereare additional version digests (step 710). If no, the method ends (step728). If yes, the method 700 searches for the digest value in the hashtable, checks all digest values in the sequential buffer pointed fromthe hash table bucket to which the version digest value hashed to so asto verify if the reference and version digest values match and if theirblock sizes match, and also considers each data match found (step 712).In other words, for each digest value of the version, the value issearched in the hash table. All the digest values in the sequentialbuffer pointed from the hash table bucket to which the version digestvalue hashed to, are checked to verify if the reference and versiondigest values match, and if their segment sizes match. The method 700,the determines if there was at least one match is found (step 714). Ifat least one match is found, the method 700 determines if there areadditional matches (step 720). If yes, for each of the found matches,the match is extended forward and backward using the buffered storage ofthe reference digests, until the matched sequence of digests cannot befurther extended (step 722). If no, the largest matched sequence isselected (step 724). A data match metadata record is generated for theentire matched sequence. The method 700 searches the next location inthe version of the digest following the matched digest sequence (step726). The location in the version of the digest to be searched next isthe digest following the matched digest sequence. A data match isdetermined by the start offset of the first matching digest in thesequence, and the data covered by all the matching digests in thesequence.

Returning to step 714, if at least one match is not found, the method700 declares a data mismatch whose offsets and length are those of theversion digest (step 716). If no match is found, a data mismatch isdeclared, whose offsets and length are those of the version digest. Themethod 700 searches the next location in the version of the digestfollowing the mismatching digest (step 718). The location in the versionof the digest to be searched next is the digest following themismatching digest. From both step 718 and step 726, the method 700returns to step 710.

In one embodiment, the present invention provides two main optimizationsfor the above algorithm, specified in the following. A firstoptimization is that the hash table shares memory storage with thesequential buffer. Specifically, a digest entry in the hash table cancontain only a compact index pointing into the sequential buffer (e.g.assuming the buffer contains up to 64K digest entries, the index fieldsize can be 2 bytes), instead of containing the complete digestinformation. A digest entry in the buffer contains the complete digestinformation, consisting of its value, and its segment's position andsize. This optimization makes the hash table very compact, and saves aconsiderable amount of memory.

A second optimization is using information produced by a preliminarystep of similarity search, that may consist of a number of alreadyverified matching positions in the version and the reference intervals,but rather for byte-wise matching and not for digest matching). Thesepositions, denoted as anchor positions, may have served as basis fordetermining that the version and reference intervals are similar. In thepresent invention, before step 710 of FIG. 7 in the above algorithm, thedigests at the anchor positions are compared, and if matching and theirsegment sizes match, then these matches are extended forward andbackward using the buffered storage of the reference digests, until thematched sequence of digests cannot be further extended. Then each ofthese matched sequences is recorded as a data match, and the algorithmcontinues to step 710 of FIG. 7 by considering only the yet unmatchedversion digests.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that may contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wired, optical fiber cable, RF, etc., or any suitable combination of theforegoing. Computer program code for carrying out operations for aspectsof the present invention may be written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Java, Smalltalk, C++ or the like and conventionalprocedural programming languages, such as the “C” programming languageor similar programming languages. The program code may execute entirelyon the user's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention have been described above withreference to flowchart illustrations and/or block diagrams of methods,apparatus (systems) and computer program products according toembodiments of the invention. It will be understood that each block ofthe flowchart illustrations and/or block diagrams, and combinations ofblocks in the flowchart illustrations and/or block diagrams, may beimplemented by computer program instructions. These computer programinstructions may be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

These computer program instructions may also be stored in a computerreadable medium that may direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks. The computer program instructions may also beloaded onto a computer, other programmable data processing apparatus, orother devices to cause a series of operational steps to be performed onthe computer, other programmable apparatus or other devices to produce acomputer implemented process such that the instructions which execute onthe computer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the above figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, may be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. A method for storing reference digests in dualdata structures in a digest based data matching process in a datadeduplication system using a processor device in a computingenvironment, comprising: determining a repository data interval assimilar to an input data interval; and loading the reference digestscorresponding to the repository data interval into dual data structures,wherein the dual data structures include a sequential buffer containinga plurality of digest entries in a sequence corresponding to a placementorder of calculated values of the reference digests, the placement orderof the calculated values of the reference digests correlative to anorder in which input digest values were calculated such that theplurality of digests are stored in a linear form independent of adeduplicated form by which data the plurality of digests describe isstored.
 2. The method of claim 1, further including applying asimilarity search process for determining the repository data intervalas similar to an input data interval.
 3. The method of claim 1, furtherincluding using the reference digests loaded into the dual datastructures to find and extend sequences of matching pairs of referenceand input digests, and producing data matches based on the sequences ofmatching pairs of reference and input digests.
 4. The method of claim 1,further including specifying an interval of data by a starting positionand a size.
 5. The method of claim 1, further including defining adigest entry to include a digest value and a segment position in dataand a segment size; and defining the search structure to be a hashtable.
 6. The method of claim 1, further including using the referencedigests stored in the sequential buffer for extending a single pair ofmatching reference and input digests into a sequence of pairs ofmatching reference and input digests comprising additional adjacentpairs of matching reference and input digests.
 7. The method of claim 1,further including storing the reference digests in a search structureand including, in each of the plurality of digest entries in the searchstructure, a position of the reference digest in the sequential buffer.8. A system for storing reference digests in dual data structures in adigest based data matching process in a data deduplication system of acomputing environment, the system comprising: the data deduplicationsystem; the dual data structures in the data deduplication system; ahash table included in the data deduplication system; a repositoryoperating in the data deduplication system; and at least one processordevice operable in the computing storage environment for controlling thedata deduplication system, wherein the at least one processor device:determining a repository data interval as similar to an input datainterval; and loading the reference digests corresponding to therepository data interval into the dual data structures, wherein the dualdata structures include a sequential buffer containing a plurality ofdigest entries in a sequence corresponding to a placement order ofcalculated values of the reference digests, the placement order of thecalculated values of the reference digests correlative to an order inwhich input digest values were calculated such that the plurality ofdigests are stored in a linear form independent of a deduplicated formby which data the plurality of digests describe is stored.
 9. The systemof claim 8, wherein the at least one processor device applies asimilarity search process for determining the repository data intervalas similar to an input data interval.
 10. The system of claim 8, whereinthe at least one processor device uses the reference digests loaded intothe dual data structures to find and extend sequences of matching pairsof reference and input digests, and producing data matches based on thesequences of matching pairs of reference and input digests.
 11. Thesystem of claim 8, wherein the at least one processor device specifiesan interval of data by a starting position and a size.
 12. The system ofclaim 8, wherein the at least one processor device: defines a digestentry to include a digest entry value and a segment position in data anda segment size; and defines the search structure to be a hash table. 13.The system of claim 8, wherein the at least one processor device usesthe reference digests stored in the sequential buffer for extending asingle pair of matching reference and input digests into a sequence ofpairs of matching reference and input digests comprising additionaladjacent pairs of matching reference and input digests.
 14. The systemof claim 8, wherein the at least one processor device stores thereference digests in the search structure and including, in each of theplurality of digest entries in the search structure, a position of thereference digest in the sequential buffer.
 15. A computer programproduct for storing reference digests in dual data structures in adigest based data matching process in a data deduplication system usinga processor device in a computing environment, the computer programproduct comprising a non-transitory computer-readable storage mediumhaving computer-readable program code portions stored therein, thecomputer-readable program code portions comprising: an executableportion that determines a repository data interval as similar to aninput data interval; and an executable portion that loads the referencedigests corresponding to the repository data interval into dual datastructures, wherein the dual data structures include a sequential buffercontaining a plurality of digest entries in a sequence corresponding toa placement order of calculated values of the reference digests, theplacement order of the calculated values of the reference digestscorrelative to an order in which input digest values were calculatedsuch that the plurality of digests are stored in a linear formindependent of a deduplicated form by which data the plurality ofdigests describe is stored.
 16. The computer program product of claim15, further including an executable portion that applies a similaritysearch process for determining the repository data interval as similarto an input data interval.
 17. The computer program product of claim 15,further including an executable portion that uses the reference digestsloaded into the dual data structures to find and extend sequences ofmatching pairs of reference and input digests, and producing datamatches based on the sequences of matching pairs of reference and inputdigests.
 18. The computer program product of claim 15, further includingan executable portion that specifies an interval of data by a startingposition and a size.
 19. The computer program product of claim 15,further including an executable portion that defines a digest entry toinclude a digest entry value and a segment position in data and asegment size; and an executable portion that defines the searchstructure to be a hash table.
 20. The computer program product of claim15, further including an executable portion that uses the referencedigests stored in the sequential buffer for extending a single pair ofmatching reference and input digests into a sequence of pairs ofmatching reference and input digests comprising additional adjacentpairs of matching reference and input digests.
 21. The computer programproduct of claim 15, further including an executable portion stores thereference digests in the search structure and including, in each of theplurality of digest entries in the search structure, a position of thereference digest in the sequential buffer.